We focus so much on documentation and description for the mechanics of data at rest, in software development. Schema for databases. Well-named variables in code, with comments. Expressive languages for writing software or querying graphs of information.
As data crosses these boundaries, though, context is lost. We reinvent the wheel at each layer! The front-end code has its own mechanism for putting a label before a value to the user. It is rare that there are less than three representations of an important piece of data across:
Manyfest's purpose is to solve this problem by creating a simple pattern to describe, validate, manipulate and interpret data.
Man-E-Faces approves of Manyfest!
Either of a stand-alone library in node.js software, or, a dependency-free browser library.
This library is tested for node.js versions 8 through 16, and will likely work in future versions. It is implemented as a simple set of es6 classes.
The browser version has been packaged into a minified as well as an expanded debuggable library. Sourcemaps are included.
For use within node.js, run the following in the folder with your package.json file:
npm install --save Manyfest
Then, you can include it in your source code as follows:
const libManyfest = require('Manyfest');
// Construct a Manyfest with a few defined columns
let animalManyfest = new libManyfest(
{
"Scope": "Animal",
"Descriptors":
{
"IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer", "Default":0 },
"Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
"Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." }
}
});
// Make up a cute and furry test creature
let testAnimal = {IDAnimal:8675309, Name:'BatBrains', Type:'Lab', Color:'Brown'};
// Validate an Object Against the Manyfest
let validateResults = animalManyfest.validate(testAnimal);
console.log(JSON.stringify(validateResults,null,4));
The code above sets up a Manyfest, and runs a validation on the testAnimal. The validation will come back all good telling us which properties aren't in the object but are described. If the strict option has been set, missing described elements of an object without data are treated as errors. If there are any Required columns, they are always errors if they are missing.
Error does not mean the software throws an exception. It comes back as well-formed JSON.
Below is a lexicon of terms used throughout this documentation. If you see anything missing, want more elaboration or just dislike a particular term, please file an issue in github!
| Term | Description |
|---|---|
| Scope | The scope of this representation; generally the clustered or parent record name (e.g. Animal, User, Transaction, etc.) -- does not have functional purpose; only for information and logging. |
| Schema | The stateful representation of an object's structural definition. |
| Element | A defined element of data in an object. |
| Address | The address where that data lies in the object. |
| Hash | A unique within this scope string-based key for this element. Used for easy access of data. |
| Descriptor | A description of an element including data such as Name, NameShort, Hash, Description, and other important properties. |
| Name | The name of the element. Meant to be the most succinct human readable name possible. |
| NameShort | A shorter name for the element. Meant to be useful enough to identify the property in log lines, tabular views, graphs and anywhere where we don't always want to see the full name. |
| Description | A description for the element. Very useful when consuming other APIs with their own terse naming standards (or no naming standards)! |
| Required | Set to true if this element is required. |
Okay so these are a lot of crazy words. The important two are Address and Hash. Every element in a schema must have an address. Having a hash just multiplies the usefulness of these addresses.
Addresses are meant to be kinda magic. They describe locations in nested JSON just as well as simple objects. Further, they can allow us to manipulate and read JSON values at specific addresses.
Let's use our Animal schema and extend it a little bit. In this case, a new JSON sub object needs to be included carrying important medical information about this animal.
let animalManyfest = new libManyfest(
{
"Scope": "Animal",
"Descriptors":
{
"IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" },
"Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
"Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." },
"MedicalStats":
{
"Name":"Medical Statistics", "Description":"Basic medical statistics for this animal"
},
"MedicalStats.Temps.MinET": { "Name":"Minimum Environmental Temperature", "NameShort":"MinET", "Description":"Safest minimum temperature for this animal to survive in."},
"MedicalStats.Temps.MaxET": { "Name":"Maximum Environmental Temperature", "NameShort":"MaxET", "Description":"Safest maximum temperature for this animal to survive in."},
"MedicalStats.Temps.CET":
{
"Name":"Comfortable Environmental Temperature",
"NameShort":"Comf Env Temp",
"Hash":"ComfET",
"DataType":"Float",
"Description":"The most comfortable temperature for this animal to survive in."
}
}
});
Notice in this example, the addresses are more complex. They have a dot syntax. This notifies Manyfest that they are nested values. Further, there is both a Name and a NameShort descriptor setup. This gives us a framework for consistently referring to the data element both internally and to the user. It is no longer a mystery what someAnimal.MedicalStats.Temps.CET means. Developers, user interface designers, database engineers, product managers and other folks who work on the software side don't have to maintain a third body of documentation about what the data means.
To aid in this discovery, reference and such, we've given it a NameShort (for use in things like tabular views and graphs/charts), a longer Name and a Hash (to enable easy reading and writing using the object element read/write functions described later in this documentation).
| Type | Description |
|---|---|
| String | A pretty basic string |
| Integer | An integer number |
| Float | A floating point number; does not require a decimal point |
| Number | A number of any type |
| PreciseNumber | An arbitrary precision number, stored in a string |
| Boolean | A boolean value represented by the JSON true or false |
| Binary | A boolean value represented as 1 or 0 |
| YesNo | A boolean value represented as Y or N |
| DateTime | A javascript date |
| Array | A plain old javascript array |
| Object | A plain old javascript object |
| Null | A null value |
Lastly, when working with objects, Manyfest provides a set of functions to read and write from/to these element addresses. This can be useful for consistently accessing objects across boundaries as well as filling out element defaults without requiring a crazy amount of boilerplate code.
For instance, if you have an element with the address of "MedicalStats.HeartRate.RestingHeartRate.OverallAverage" (which is very verbose; most JSON object structures are not so descriptive) it would take a significant amount of code to write that to an empty object.
In the example below, the read and write code throws an error. You could work around it with:
someObject.?SomeContainer.?OtherContainer.Property (although that isn't compatible with older services and browsers that run older versions of javascript)// Write Code
let newAnimal = {};
// This is going to make a terrible error happen
newAnimal.MedicalStats.HeartReat.RestingHeartRate.OverallAverage = 61;
// Read Code
let newAnimal = {};
// This is going to make a terrible error happen
console.log(newAnimal.MedicalStats.HeartReat.RestingHeartRate.OverallAverage);
// My javascript interpreter said this when I tried this code:
// > Uncaught TypeError: Cannot read properties of undefined (reading 'HeartReat')
However with the Manyfest reading and writing methods you can do this (all in one example since it doesn't blow up):
let newAnimal = {};
// You can now try to access the value on a "clean" object...
console.log(animalManyfest.getValueAtAddress(newAnimal, "MedicalStats.HeartRate.RestingHeartRate.OverallAverage"));
// The output prints out "undefined" ... because it is!
// This will be helpful and create the necessary structure inbetween
animalManyfest.setValueAtAddress(newAnimal, "MedicalStats.HeartRate.RestingHeartRate.OverallAverage", 61);
// You can now access the value as well...
console.log(animalManyfest.getValueAtAddress(newAnimal, "MedicalStats.HeartRate.RestingHeartRate.OverallAverage"));
// The output prints out "61"
Because we have mappings to and from more human readable names to the addresses, we can happily use either the Name or Hash for these lookups. For instance, from the example above, if we have our Comfortable Environmental Temperature for an animal which was in the address someAnimal.MedicalStats.Temps.CET and had a hash of ComfET, a developer could easily access it by hash (assuming the favoriteAnimalAPI function returns a JSON representation of my favorite animal):
let favAnimal = favoriteAnimalAPI();
console.log(animalManyfest.getValueByHash(favAnimal,'ComfET'));
For any elements that haven't defined a Hash, the Address is used. This allows code to gracefully fall back.
Sometimes we want to reuse the structure of a schema, but look up values by hash using translations.
Sometimes we don't have schemas, and want to define object element structure on the fly. This can be done programmatically. As a refresher, here is how we loaded our simplest schema manifest above:
const libManyfest = require('Manyfest');
// Construct a Manyfest with a few defined columns
let animalManyfest = new libManyfest(
{
"Scope": "Animal",
"Descriptors":
{
"IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" },
"Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
"Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." }
}
});
The programmatic equivalent is the following code:
const libManyfest = require('Manyfest');
// Construct a Manyfest with a few defined columns
let animalManyfest = new libManyfest();
// Set the Scope
animalManyfest.Scope = "Animal";
// Add descriptors
animalManyfest.addDescriptor("IDAnimal", { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" });
animalManyfest.addDescriptor("Name", { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." });
animalManyfest.addDescriptor("Type", { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." });
// Now you can work with the animalManyfest just as we did in the other method.
Programmatic definition is interesting because you can start with a pre-defined manifest and add on elements later if you like. This can be useful if you, say, have an endpoint which generally returns a record, but, sometimes decorates it with connected records for developer convenience.
Have you ever tried to code against a weather API? They use so many different structures of data. And once you've used their structure, you are kindof stuck with it.
With manyfest, you can easily create a description for each API and code against getting values by hash. This abstracts the complexity of multiple API services without requiring you to marshal it into your own persistence format.
Modern APIs are super complicated. And worse, they change. Let's take a real example. Archive.org is a wonderful resource for downloading awesome content gathered from the web and such.
There is an API to access their data. It's ... really messy, the data you get back. below is the JSON for a single video (a rad Count Chocula commercial from 1971) -- it takes quite a bit of scroll to get down to the bottom.
{
"created": 1664830085,
"d1": "ia600202.us.archive.org",
"d2": "ia800202.us.archive.org",
"dir": "/7/items/FrankenberryCountChoculaTevevisionCommercial1971",
"files": [
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000001.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336956",
"size": "838",
"md5": "e47269cd5a82db9594f265a65785ec12",
"crc32": "165c668b",
"sha1": "383303d9546c381267569ad4e33aff691f0bb8c7"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000004.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336957",
"size": "6843",
"md5": "c93fa52000ab4665e69b25c403e11aff",
"crc32": "9444e6f6",
"sha1": "716b4f9950b8147f51d3265f9c62ff86451308d5"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000009.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336957",
"size": "8388",
"md5": "30eb3eb4cbbdfa08d531a0a74da7c000",
"crc32": "be874a9e",
"sha1": "0c392d777609e967b6022be27edad678c5ae74e2"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000014.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336958",
"size": "5993",
"md5": "4e9ebc3d076bec8cf7dfe76795f8c769",
"crc32": "912ec98c",
"sha1": "01dc49c852e1bbb421199450dd902935c62b06de"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000019.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336958",
"size": "4951",
"md5": "59f190f0c5b0a048415b26412860b6dd",
"crc32": "a70a30b1",
"sha1": "a284af9757cb24d28f96ec88ec1b1c23a8cea9fe"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000024.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336959",
"size": "3383",
"md5": "be2a908acd563b896e7758b598295148",
"crc32": "ed467831",
"sha1": "94c001e72ebc86d837a78c61a004db9ab9d597bd"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971.thumbs/frankerberry_countchockula_1971.0001_000029.jpg",
"source": "derivative",
"format": "Thumbnail",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336960",
"size": "3503",
"md5": "c82199d09be07633000fd07b363dd8a3",
"crc32": "a1fd79cb",
"sha1": "2bc8e761edb24a441fa5906dda1c424e1f98a47a"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971_archive.torrent",
"source": "metadata",
"btih": "de6b371e7cc3c83db1cc08150500753eae533409",
"mtime": "1542761794",
"size": "4093",
"md5": "a275d3b4028cccb5bea8b47a88c838af",
"crc32": "5ffa7334",
"sha1": "af8222637b574cba1360d0ea77e231640ffd43c4",
"format": "Archive BitTorrent"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971_files.xml",
"source": "metadata",
"format": "Metadata",
"md5": "3a7e87b08bed1e203a5858b31352c110"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971_meta.xml",
"source": "metadata",
"format": "Metadata",
"mtime": "1542761793",
"size": "1371",
"md5": "0b9c9bf21b9a26aea43a2f735b404624",
"crc32": "41077288",
"sha1": "22e6f2c73bf63072f671d846355da2785db51dbd"
},
{
"name": "FrankenberryCountChoculaTevevisionCommercial1971_reviews.xml",
"source": "original",
"mtime": "1466898697",
"size": "620",
"md5": "260bfba5d696772445dcc7ff6e6d5bdb",
"crc32": "25ea3229",
"sha1": "7d541f18fcd5ad9c6e593afe5a80f18771f23b32",
"format": "Metadata"
},
{
"name": "__ia_thumb.jpg",
"source": "original",
"mtime": "1539115881",
"size": "7481",
"md5": "8cec324fa0016fd77cc04e6a4b2ebb00",
"crc32": "d9e1b316",
"sha1": "4dab42952fe0405a3b7f80146636b33d7b1bd01e",
"format": "Item Tile",
"rotation": "0"
},
{
"name": "frankerberry_countchockula_1971.0001.gif",
"source": "derivative",
"format": "Animated GIF",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336965",
"size": "101114",
"md5": "b78a13094030f104900eb996bafe2b7d",
"crc32": "6650cd8",
"sha1": "669798c037205cac14f70592deef6f7831b3d4a1"
},
{
"name": "frankerberry_countchockula_1971.0001.mpg",
"source": "original",
"format": "MPEG2",
"mtime": "1296335803",
"size": "31625216",
"md5": "762ba18b026b85b3f074523e7fcb4db0",
"crc32": "42347f78",
"sha1": "41162dc2d1a91b618124c84628d0c231544a02be",
"length": "31.14",
"height": "480",
"width": "640"
},
{
"name": "frankerberry_countchockula_1971.0001.mpg.idx",
"source": "derivative",
"format": "Video Index",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336956",
"size": "31141",
"md5": "49423e072726e4ea3cdd8ebdd26c7dfc",
"crc32": "ae969a68",
"sha1": "805782cd2d0f9002555816daadf3b8607e621f79"
},
{
"name": "frankerberry_countchockula_1971.0001.ogv",
"source": "derivative",
"format": "Ogg Video",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336994",
"size": "2248166",
"md5": "f1b933e97ce63594fb28a0a019ff3436",
"crc32": "a2a0e5e9",
"sha1": "a6bf0aec9f006baeca37c03f586686ebe685d59b",
"length": "31.15",
"height": "300",
"width": "400"
},
{
"name": "frankerberry_countchockula_1971.0001_512kb.mp4",
"source": "derivative",
"format": "512Kb MPEG4",
"original": "frankerberry_countchockula_1971.0001.mpg",
"mtime": "1296336977",
"size": "2378677",
"md5": "a7750839519c61ba3bb99fc66b32011d",
"crc32": "4dbd37c8",
"sha1": "3929314c192dec006fac2739bcb4730788e8c068",
"length": "31.13",
"height": "240",
"width": "320"
}
],
"files_count": 17,
"item_last_updated": 1542761794,
"item_size": 36431778,
"metadata": {
"identifier": "FrankenberryCountChoculaTevevisionCommercial1971",
"title": "Franken Berry / Count Chocula : Tevevision Commercial 1971",
"creator": "General Mills",
"mediatype": "movies",
"collection": [
"classic_tv_commercials",
"television"
],
"description": "Count Chocula and Franken Berry were both introduced in 1971. Boo Berry Cereal appeared in 1973 followed by Fruit Brute in 1974. Yummy Mummy appeared more than a decade later in 1988 - completing the the group known as the General Mills Monster Cereals.",
"subject": "Third Eye Cinema; Classic Television Commercials; animation; cartoons;General Mills",
"licenseurl": "http://creativecommons.org/publicdomain/mark/1.0/",
"publicdate": "2011-01-29 21:36:42",
"addeddate": "2011-01-29 21:35:38",
"uploader": "bolexman@msn.com",
"updater": [
"Bolexman",
"Bolexman",
"Jeff Kaplan"
],
"updatedate": [
"2011-01-29 21:45:38",
"2011-01-29 21:55:46",
"2011-01-29 23:04:55"
],
"sound": "sound",
"color": "color",
"runtime": "0:31",
"backup_location": "ia903608_22",
"ia_orig__runtime": "31 seconds"
},
"reviews": [
{
"reviewbody": "Sugar cereal cartoon Karloff and Lugosi argue self-importance pre Lorre ghost. Interesting how kids still know the voices without any idea of the origins.",
"reviewtitle": "pre booberry",
"reviewer": "outofthebox",
"reviewdate": "2016-06-25 23:51:36",
"createdate": "2016-06-25 23:51:36",
"stars": "4"
}
],
"server": "ia800202.us.archive.org",
"uniq": 1957612749,
"workable_servers": [
"ia800202.us.archive.org",
"ia600202.us.archive.org"
]
}
With just a small number of element descriptors, we can make this huge blob of JSON very usable for a developer.
{
"Scope": "Archive.org",
"Descriptors": {
"d1": {
"Hash": "Server",
"Name": "Server",
"Description": "The primary server to download these files from.",
"DataType": "String"
},
"d2": {
"Hash": "ServerAlternate",
"Name": "Alternate Server",
"Description": "The alternate server to download these files from.",
"DataType": "String"
},
"dir": {
"Hash": "Path",
"Name": "Server URL Path",
"NameShort": "Path",
"Description": "The path on the server where these files are located."
},
"metadata.identifier": {
"Hash": "GUID",
"Name": "Globally Unique Identifier",
"NameShort": "GUID",
"Description": "Archive.org unique identifier string."
},
"metadata.title": {
"Hash": "Title",
"Name": "Title",
"NameShort": "Title",
"Description": "The title of the media item."
},
"metadata.creator": {
"Hash": "Creator",
"Name": "Creator",
"NameShort": "Creator",
"Description": "The creator of the media item."
},
"metadata.mediatype": {
"Hash": "Type",
"Name": "Media Type",
"NameShort": "Type",
"Description": "The type of media item."
}
}
}
These two JSON files are in the examples/chocula folder along with a javascript file Chocula.js you can try out yourself and hack on.
let libManyfest = require('../../source/Manyfest.js');
let dataArchiveOrg = require(`./Data-Archive-org-Frankenberry.json`);
let schemaArchiveOrg = require(`./Schema-Archive-org-Item.json`);
let _Schema = new libManyfest(schemaArchiveOrg);
console.log(`The URL for "${_Schema.getValueByHash(dataArchiveOrg,'Title')}" is: ${_Schema.getValueByHash(dataArchiveOrg,'Server')}${_Schema.getValueByHash(dataArchiveOrg,'Path')}`);
Change the complex address resolution functions to leverage a single resolver that returns both container and entry.
FAQs
JSON Object Manifest for Data Description and Parsing
The npm package manyfest receives a total of 72 weekly downloads. As such, manyfest popularity was classified as not popular.
We found that manyfest demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.